Managing a multi-supplier environment

ABSTRACT

The present disclosure is directed to a system and method for managing multi-supplier environment. In some implementations, a method includes identifying a supplier model configured to identify information for executing different aspects of the transaction associated with different enterprise departments and a primary supplier from a plurality of selectable third-party suppliers in response to at least a request for a enterprise transaction. The model is configured to identify methodologies for executing the different aspects of a transaction. A plurality of requests for the different enterprise departments and the primary supplier are generated based, at least in part, on the supplier model and the transaction request. Each of the different enterprise departments and the primary supplier are associated with at least one of the plurality of requests. Each of the plurality of requests are automatically transmitted to at least one of the associated enterprise departments or the primary supplier in accordance with the supplier model.

TECHNICAL FIELD

This invention relates to data communication and, more particularly, tomanaging a multi-supplier environment.

BACKGROUND

Providing goods and services typically requires an enterprise to performmultiple tasks or other entities to perform associated tasks. Thesetasks may include the use of software, hardware, or other technology. Inaddition, these tasks may also require that individuals perform certainmanagement or supporting tasks. These tasks can be fairly complexrequiring multiples steps and/or processes. Frequently, enterprisesoptimize such processes by using one or more of the followingInternational Standards, frameworks and/or best practices: ITIL ver2,ITIL ver3 (Released May 2007), ISO/IEC 20000 (Released April 2007), CMMIACQ & SRV v1.2, COBIT4.0, ISO 17799 and eSCM-SP v2. Design For Six Sigmaframework (DFSS) & Lean Six Sigma.

SUMMARY

The present disclosure is directed to a system and method for managingmulti-supplier environment. In some implementations, a method includesidentifying a supplier model configured to identify information forexecuting different aspects of the transaction associated with differententerprise departments and a primary supplier from a plurality ofselectable third-party suppliers in response to at least a request for aenterprise transaction. The model is configured to identifymethodologies for executing the different aspects of a transaction. Aplurality of requests for the different enterprise departments and theprimary supplier are generated based, at least in part, on the suppliermodel and the transaction request. Each of the different enterprisedepartments and the primary supplier are associated with at least one ofthe plurality of requests. Each of the plurality of requests areautomatically transmitted to at least one of the associated enterprisedepartments or the primary supplier in accordance with the suppliermodel.

In some aspects of operation, the disclosure may provide amulti-supplier model that has one or more of the following properties:dynamic as it can scale to fit most enterprise environment andindustries; flexible as it can be used in total, partial or justselected modules; evolving with built in intelligence to adapt andimprove; ease of use the model is logical and may not need specialtools; transparency support as running in the background of multipleimplementation; governance introduce governance to “Data in Motion”across an enterprise; compliant with Best Practices, Standards andFrameworks and has been mapped to, for example, ITIL v3, and/or others.

The details of one or more embodiments of the invention are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the invention will be apparent from thedescription and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a management system in accordance with some implementations ofthe present disclosure;

FIG. 2 is an example supplier model of FIG. 1 in accordance with someimplementations of the present disclosure;

FIG. 3 is a flow chart illustrating an example for generating a suppliermodel;

FIG. 4 is an example flow chart illustrating that parallel processes inaccordance with some implementations of the present disclosure; and

FIG. 5 is an example diagram illustrating data and processes in themanagement system of FIG. 1.

DETAILED DESCRIPTION

FIG. 1 is a management system 100 for managing a multi-supplierenvironment in accordance with some implementations from the presentdisclosure. For example, the system 100 may manage third-party suppliersin accordance with a previously generated supplier model. In someimplementations, the system 100 can implement supplier models forservice management, business transformation, common services, automationimplementation and/or standards/frameworks assessment and audits. Asupplier model may include technical information (e.g., data format,network interface, application interface), logical information (e.g.,workflow, supplier hierarchy) as well as other information for executinga transaction. In some implementations, a transaction may includetransmitting requests, interfacing third-party suppliers, legal andcontractual approvals, routing transactions for approval, billing,and/or other as aspects of transactions. For example, the system 100 mayprovide the ability to manage the development, acquisition and/ormaintenance of products and/or services supplied to an enterprise fromdifferent performing suppliers at different stages of deployment. Insome implementations, the system 100 can align processes, improve themand/or ensures a high level of stability, capability and/or maturity tothe integration of different services. The system 100 may provide one ormore of the following for executing a transaction: structuredflexibility that can adapt and/or expand according to the enterprisebusiness needs and/or requirements; independent layers that can be runas separate offerings without loosing the links to the other layers;built in continuous improvement loops that strengthen and/or enhance thesupplier model robustness; overall understanding of the total servicemanagement life cycle; and/or others. In some implementations, thesystem 100 can provide an end-to-end methodology that covers enterpriserequirements in a multi-supplier environment.

At a high level, the system 100 includes an enterprise network 102coupled to suppliers 104 a-c through a network 106. The enterprisenetwork 102 includes a plurality of enterprise departments 103, havingassets 108, are configured to manage or otherwise process differentaspects of transactions with the suppliers 104 a-c in accordance withone or more multi-supplier models 110. The models 110 may identifyinstructions, guidelines, or directives for identifying, transmitting,servicing, or otherwise processing transactions for products and/orservices. For example, an asset 108 may automatically transmit one ormore documents and/or information formatted for particular departments103 and supplier 104 in accordance with the model 110. In response to atleast a request, the suppliers 104 may provide products and/or servicesin accordance with the associated model 110. For example, the supplier104 may follow methodologies identified in the model to verify approval,provide services, invoice the services, and/or other aspects. In someimplementations, a primary supplier 104 a may transmit the request to asecondary supplier 104 d in accordance with the associate model 110.

As for a more detailed description of the elements, the enterprisenetwork 102 is a network associated with an enterprise. The enterprisemay comprise a corporate or business entity, a government body, anon-profit institution, or any other organization with a plurality ofassets 108. The enterprise may be the owner of assets 108. Of course,the enterprise may also lease assets 108 or may hire contractors oragents who are responsible for maintaining, configuring, controlling,and/or managing assets 108. In the illustrated implementation, theenterprise network 102 includes a plurality of departments 103. Thedepartments 103 may associated with different aspects of the enterprisesuch as research and development, accounting, production, legal, and/orother departments. In some implementations, execution of a transactionmay include approval or at least processing from multi departments 103.Multiple departments 103 may automatically coordinate the differentaspects of a transaction using the multi-supplier models 110. In someembodiment, the enterprise manages the requests for third-party productsand/or services through the enterprise network 102. For example, theenterprise may manage requests to suppliers 104 in accordance with oneor more models 110.

In the illustrated embodiment, the enterprise network 102 facilitateswireless and/or wireline communication between the assets 108 and/or thenetwork 106. The enterprise network 102 may communicate, via a mediumfor example, Internet Protocol (IP) packets, Frame Relay frames,Asynchronous Transfer Mode (ATM) cells, voice, and/or video, data, andother suitable information (for example graphs or drawings) betweennetwork addresses identified internal or external to the enterprisefollowing a selective path and work flow depending on the nature of therequest raised. In addition, while the enterprise network 102 isillustrated as a single network, the enterprise network 102 may comprisea plurality of networks related, for example, to different activities,departments within the enterprise, and/or hierarchical splits. In short,the enterprise network 102 is any suitable network that includes assets108.

As described above, the assets 108 comprise devices associated with theenterprise and may include computers, servers, routers, data storagedevices, a personal computer, a workstation, network computer, personaldata assistant (PDA), one or more processors within these or otherdevices, or any other suitable processing device. Each asset 108 may beassociated with a group 103 and/or an individual within a department103. For example, a group of assets 108 may be associated with acorporate department 103 (e.g., accounting, marketing, research anddevelopment), a geographic or network (sub-net) region (e.g., UnitedStates, Europe), a location (e.g., building, floor in building), acustomized group (e.g., “Bill's Group”), or any other suitablecategorization of assets 108. Each asset 108 executes, references,includes, or is otherwise associated with requests for products and/orservices from one or more suppliers 104. In the illustratedimplementation, the assets 108 can direct requests and/or other actionsassociated with requested products and/or services (e.g., accounting) inaccordance with one or more models 110.

Supplier models 110 comprises any rules, instructions, algorithms, code,spreadsheets, flow charts, work flows and/or other directives used byassets 108 and/or suppliers 104 to execute transactions. For example,the multi-supplier model 110 may include one or more entries or datastructures that identify a product, process information (e.g.,implementation), billing information, and/or other data. In someimplementations, the multi-supplier model 110 may include informationassociated with one or more of the following: process, interface, event,roles & responsibilities, task, tool, information source, work flow,output, view & presentation, audit & security, error handling, and/orother information. For example, the multi-supplier model 110 may providebest practices for executing a transaction. In addition, themulti-supplier model 110 may include directives for implementingidentified methods, workflows, and/or other actions. For example, themulti-supplier model 110 may include or identify technology, processes,and/or people to implement the methodologies modeled by the associatedsupplier model 110. For example, the multi-supplier model 110 mayidentify a plurality of documents associated with different departments103, automatically populate the documents with information and transmitthe information to the appropriate departments 103. As mentioned above,the multi-supplier model 110 may include a workflow to replace anexisting activity in a transaction. In some implementations, themulti-supplier model 110 may include or otherwise identify code to usein satisfying, for example, a request. In addition, the enterprise mayperiodically replace or modify technology, processes and/or workflows inthe multi-supplier model 110. The multi-supplier model 110 may include apresentation layer to enable a complete view of incidents and/or servicerequests investigated or supplied from multiple suppliers, displayed ona WEB portal, taking into consideration the appropriate securitymeasures, conforming with data privacy acts and able to monitor supplierperformance to drive the rectification of errors in operations and/ordelivery of service in minimum delays.

Methodologies included in the multi-supplier model 110 may be usable byhumans, devices, or a combination of the two. In some implementations,the data used in the multi-supplier model 110 may be stored or processedin any suitable format such as, for example, a text file, binary file,an XML document, a flat file, a comma-separated value (CSV) file, aname-value pair file, structured query language (SQL) table, one or morelibraries, or others. The multi-supplier model 110 may be dynamicallycreated or populated by one or more assets 108, a third-party vendor,any suitable user of the enterprise network 102, loaded from a template,or received via network 106. The term “dynamically” as used herein,generally means that the appropriate processing is determined atrun-time based upon the appropriate information.

Suppliers 104 a-c comprises an electronic device (e.g., computingdevice) operable to receive, transmit, process and store informationassociated with requests from the enterprise network 102. For example,the supplier 104 may receive a request for software updates from theasset 108 and transmit and bill for the update in accordance to anassociated model 110. In general, the supplier 104 may execute one ormore of the following: receive requests from the enterprise network 102that was initiated by assets 108 then approved by departments 103;identify one or more models 110 associated with the request; determineability to satisfy request; transmit request to different supplier 104in accordance with the associated model 110; provide services and/orproducts to the network 102 in accordance with the multi-supplier model110; and/or other functions. In some implementations, the supplier 104is a third-party supplier. The suppliers 104 may be ranked such thatsuppliers 104 are contact in particular order. For example, themulti-supplier model 110 may identify the supplier 104 a as a primaryprovider while the supplier 104 d is a secondary supplier. In the casethat the primary supplier 104 a is not able to satisfy a request, theprimary supplier 104 a may transmit the request to the second supplier104 d in accordance with the multi-supplier model 110. Supplier 104 dfulfill the request deliver the service in accordance to themulti-supplier model 110 and bill supplier 104 a for the service. Atthis stage supplier 104 a will raise an invoice to enterprise 102 forpayment. The RtP (Request to Pay) may be routed to the correctdepartment 103 follow the selected path as per the multi-supplier model110 and reach Accounts Payable after receiving approvals per themulti-supplier model 110 and automatically release the payment tosupplier 104 a who may in turn will pay supplier 104 d for the serviceor product provided.

Network 106 facilitate wireless or wireline communication between server106 and any other local or remote computer, such as assets 108 andsuppliers 104. Network 106 may be all or a portion of an enterprise orsecured network. While illustrated as single network, network 106 may bea continuous network logically divided into various sub-nets or virtualnetworks without departing from the scope of this disclosure, so long asat least portion of network 106 may facilitate communications oftransaction requests between suppliers 104 and at least one asset 108.In some implementations, network 106 encompasses any internal orexternal network, networks, sub-network, or combination thereof operableto facilitate communications between various computing components in thesystem 100. Network 106 may include one or more local area networks(LANs), radio access networks (RANs), metropolitan area networks (MANs),wide area networks (WANs), all or a portion of the global computernetwork known as the Internet, and/or any other communication system orsystems at one or more locations.

In one aspect of operation, the multi-supplier model 110 may be a methodof integrating multiple performing suppliers 104 for a singleenterprise's organization by establishing a virtual environment (e.g.,transparent to users) of an end-to-end service management. For example,the multi-supplier model 110 may cover one or more of the following:activities performed by end users raising issue, middle ware, serviceprovider front desk, technician on site, recovery of service, closure ofissue, internal billing, client facing contract and legal. Associatedinformation may be displayed in a single view (e.g., WEB based portal).In some implementations, the system 100 may execute one or more of thefollowing: collect information by performing an enterprise serviceassessment that will define organization strategies and develop itsservice portfolio; investigate each process in order to optimize itsfunction and deliver a complete process documentation and servicecatalogue; compare and challenge each documented process against bestpractices in its category in order to improve each process and raise itsstandard; provide a vendor management office and a complete enterprisedata model structure; investigate the delivery of each process, itsinterface and the way it integrates with other processes in order toselect the best technology solution and partner to automate them;provide a suitable technology solution catering for flexibility,expandability, scalability and maximum leveragability and reusability ofits modules; implement and deploy the proposed solution via a controlledmanagement of change affecting the whole organization; provide a totalsolution of multiple supplier integration to the operation management tomaintain and sustain while looking continuously for methods ofimprovement; and/or others.

FIG. 2 illustrates an example model 110 of FIG. 1 in accordance withsome implementations of the present disclosure. It will be understoodthat the illustrated model is for example purposes only. Accordingly,the system 100 may include or present information in any format ordescriptive language, and each page may present any appropriateadvertising information in any layout without departing from the scopeof the disclosure.

In particular, the multi-supplier model 110 includes modules 202 andassociated parameters 204 for executing actions associated with arequest for services and/or products. For example, the multi-suppliermodel 110 may include a billing module that identifies a process andinformation for billing for services provided to the enterprise network102. In the illustrated implementation, the multi-supplier model 110includes the following modules 202: process, interface, event, roles &responsibilities, task, tool, information source, work flow, output,view & presentation, audit & security, and error handling. Though, themulti-supplier model 110 may include some, all, or none of theseillustrated modules 202 without departing from the scope of thisdisclosure.

Each module 202 may includes or otherwise identify associated parameters204. The process module 202 may identify the following parameters:assessment, optimization, and implementation. The interface module 202may identify the following parameters: product, client, finance,supplier, employee, and users. The event module 202 may identify thefollowing parameters: service request and incident. The roles &responsibility module 202 may identify the following parameters:responsible, approver, support, informed, and consulted. The task module202 may identify the following parameters: activity and instruction. Thetool module 202 may identify the following parameters: tool steps,templates, and forms. The information-source module 202 may identify thefollowing parameters: data type and format. The work flow module 202 mayidentify the following parameters: routing transactions for review orapproval. The output module 202 may identify the following parameters:end results or process outcome. The view & presentation module 202 mayidentify the following parameters: report, dashboard and analysis. Theaudit & security module 202 may identify the following parameters: dataprivacy, risk assessment, and activities logging and tracking. The errorhandling module 202 may identify the following parameters: restoreoperation, recover data, avoid same error, and zero outage. Theseparameters 204 are for illustration purposes only and the multi-suppliermodel 110 may include some, all or none of these parameters 204. Inaddition, these parameters 204 may be associated with different modules202 without departing from the scope of this disclosure.

FIG. 3 is a flow chart illustrating example method for maintaining asupplier model 110 of FIG. 1 in accordance with some implementations ofthe present disclosure. In general, the method 300 describes generatingone or more supplier models 110 for requesting and/or receiving servicesfrom the suppliers 104. Method 300 contemplates using any appropriatecombination and arrangement of logical elements implementing some or allof the described functionality.

At a high level, the method 300 includes seven layers: Layer 1Strategies & Servcice Portfolio, Layer 2 ProcessOptimisation—Documentation & Service Catalogue, Layer 3 Good Practices,Layer 4 Technology & Partners, Layer 5 Scalability/Leveragabilityknowledge Management, Layer 6 Managing Organisation Stakeholder Changeand Layer 7 Manage Operations Monitoring & Control. Method 300 begins atstep 302 where the current system 100 is assessed. For example, the step302 may use automated scripts and/or manual templates to collect dataand load the collected data into an assessment program to generateassessment results. Next, at step 304, the assessment information isassociated with strategies and service portfolio. For example, theassessment information may be correlated with enterprise strategies,policies, goals, and/or objectives. In some implementations, the system100 determines the current state of enterprise operations and projectedoperations after implementing the multi-supplier model 110. The step 304may include building a service portfolio in the event that a portfoliohas not been previously generated by the enterprise. In someimplementations, the building of a service portfolio may be automatedthen leveraged to other instances. At step 306, the enterprise processesare optimized. In some implementations, the optimization process mayinclude documentation and/or service catalogue. In the event that theenterprise does not have standard processes or has not documented orupdated them, the system 100 may use techniques that optimize orotherwise improve current processes. For example, the system 100 mayimplement Lean Six Sigma tools to improve the identified processes. Insome implementations, the step 306 may include one or more of thefollowing: identify interdependencies, chain reactions, performancedegradation opportunities for premium value creation, and/or othertechniques. In addition, the step 306 may include updating and/orcompleting a service catalogue of services currently offered to theenterprise such as users of assets 108. If the improved processes arenot aligned and/or validated at decision step 308, then execution ofmethod 300 returns to the step 306. If the improved processes arealigned and validated, then the identified current processes are mappedto identified practices at step 3 10. For example, the current processesmay be mapped to standard, framework and/or good practices, and/ortailored to the enterprise's environment for full or partial automation.In some implementations, the step 306 includes identifying best fittechnology and/or partners that can execute these processes. Theenterprise may elect to forgo this step in such cases as the currenttool in use is adequate, acceptable, and/or able to customize to matchthe updated processes formalized in the previous step. If the improvedprocesses are not tailored and/or accepted at decision step 312, thenexecution returns to the step 310. If the improved processes aretailored and/or accepted, then execution of the method 300 proceeds tostep 314.

At step 314, technology and partner activity are identified. Forexample, a single service or outsource supplier 104 has technologycontrolled by a single source. In the case of multiple supplier/service,the technology and/or infrastructure may be selected or recommended inaccordance with the type of integration specified for the network anddata structure and may match the identified strategies. The step 314 mayinclude negotiating and/or resolving conflicts and incompatibilities(e.g., technically, logically) between suppliers 104, network 102 andassets 108 to achieve a successful user acceptance and/or toolimplementation of the selected processes. If the technology and/orpartners are not integrated at decisional step 316, then executionreturns to step 314. If the technology and/or partners are integrated,then, at step 318, leveragability and knowledge management aredetermined. For example, this step 318 may verify that the structuredflexibility satisfies the needs and/or requirements of a scalablemulti-supplier environment. In addition, the step 318 may verify thatappropriate modeling techniques are leveraged for current and forecastedperformance, capacity and/or throughput. In some implementations, thecurrent tools can be mapped to the integration plan. If the processesare not deployable at decisional step 320, then execution returns tostep 314. If the processes are deployable at decisional step 320, thenat step 322, organization stakeholder change is managed. This step maybe executed as a logical extension of the previous steps, can beselected after the optimization and update of the enterprise processes,the addition of new manual activities and/or the implementation of newor modified tools. In some implementations, this step can be executed toaddress resistance to change, map process roles to organization rolesand/or align service integrator roles to provider roles. In someinstances, specific induction, training and education programs may bedeveloped to provide stakeholders with the skills and/or knowledge forplanning, implementing and/or sustaining process changes.

The step 324 includes managing operations when executed. For example,the step 324 may include monitoring and/or controlling the updatedprocesses. In some implementations, the multi-supplier model 110 isimplemented in response to at least implementing integrationtasks/activities scheduled in the previous steps, transferring databetween suppliers 104 and/or streamlining service delivery and supportprocesses. The step 324 may include identifying a metrics for trackingand/or monitoring business value measures, transition measures, and/orchange readiness measures. Such data may be fed to the enterprisedashboard to represent a single view in the presentation layer. Inaddition, the step 324 may also include analyzing reports generatedduring the implementation of the multi-supplier model 110, evaluatingand assess the progression of the implementation, determining lessonslearned from the implementation, and/or determining benefits ofimplementing the multi-supplier model 110.

FIG. 4 illustrates a flow chart 400 representing one or more steps ofthe method 300 of FIG. 3 in accordance with the present disclosure. Inparticular, the chart 400 includes different representations of stepsincluding the assessment and the seven layers of the multi-suppliermodel 110. As indicated, the chart 400 demonstrates that themulti-supplier model 110 may not be sequential. In illustrating severalof the steps as a parallel process, the chart 400 may have flexibility,intelligence and logic built in to address a variety of enterpriseand/or environment needs. For example, the enterprise may elect thatafter defining the strategies in Layer 1 (Step 304 in FIG. 3) to deployand executing Layer 4 (Step 314 in FIG. 3).

FIG. 5 illustrates an example consolidated diagram 500 illustrating anend-to-end view of various processes in the system 100 in accordancewith some implementations of the present disclosure. For example, thediagram 500 includes an end-to-end view data in motion, inter-relationbetween modules, and/or the different offerings in a multi-supplierenvironment.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention.

1. A method for managing a multi-supplier environment, comprising: inresponse to at least a request for an enterprise transaction,identifying a multi-supplier model configured to identify informationfor executing different aspects of the transaction associated withdifferent enterprise departments and a primary supplier from a pluralityof selectable third-party suppliers, the model configured to identifymethodologies for executing the different aspects of a transaction;generating a plurality of requests for the different enterprisedepartments and the primary supplier based, at least in part, on thesupplier model and the transaction request, each of the differententerprise departments and the primary supplier associated with at leastone of the plurality of requests; identifying a document for an aspectof the transaction associated with one of the different enterprisedepartments; automatically populating said identified document with dataassociated with a corresponding transaction aspect; and automaticallytransmitting each of the plurality of requests to at least one of theassociated enterprise departments or the primary supplier in accordancewith the multi-supplier model.
 2. The method of claim 1, furthercomprising: receiving an indication of acceptance of services providedby one of the plurality of selectable third-party suppliers; in responseto at least the acceptance, automatically transmitting to an enterpriseaccounting department a request for approving payment in accordance withthe multi-supplier model; and in response to at least receivingapproval, automatically transmitting a request to generate the paymentin accordance with the multi-supplier model.
 3. The method of claim 1,further comprising: transmitting the supplier model to each of theplurality of selectable third-party suppliers; and receiving informationassociated with different aspects of transactions from the plurality ofselectable third-party suppliers in accordance with the transmittedsupplier model.
 4. The method of claim 1, wherein the generated requestsare automatically routed to the different departments and the primarysupplier using the multi-supplier model.
 5. The method of claim 1,further comprising generating a presentation based, at least in part, onthe different aspects of the transaction, wherein transmission of databetween the different departments and the primary supplier aretransparent to a user.
 6. The method of claim 1, further comprising:determining data associated with the multi-supplier model as processedduring operation of the enterprise; and periodically updating themulti-supplier model based, at least in part, on the determined data. 7.The method of claim 1, wherein generating the plurality of requestsincludes at least one of translating data, filtering data, or routingdata between different network topologies.
 8. Software for managingtransactions comprising computer readable instructions embodied on mediaand operable to: in response to at least a request for a enterprisetransaction, identify a multi-supplier model configured to identifyinformation for executing different aspects of the transactionassociated with different enterprise departments and a primary supplierfrom a plurality of selectable third-party suppliers, the multi-suppliermodel configured to identify methodologies for executing the differentaspects of a transaction; generate a plurality of requests for thedifferent enterprise departments and the primary supplier based, atleast in part, on the multi-supplier model and the transaction request,each of the different enterprise departments and the primary supplierassociated with at least one of the plurality of requests; identify atleast one document for an aspect of the transaction associated with oneof the different enterprise departments; automatically populate said atleast one identified document with data associated with a correspondingtransaction aspect; and automatically transmit each of the plurality ofrequests to at least one of the associated enterprise departments or theprimary supplier in accordance with the multi-supplier model.
 9. Thesoftware of claim 8, further operable to: receive an indication ofacceptance of services provided by one of the plurality of selectablethird-party suppliers; in response to at least the acceptance,automatically transmit to an enterprise accounting department a requestfor approving payment in accordance with the v model; and in response toat least receiving approval, automatically transmit a request togenerate the payment in accordance with the multi-supplier model. 10.The software of claim 8, further operable to: transmit the suppliermodel to each of the plurality of selectable third-party suppliers; andreceiving information associated with different aspects of transactionsfrom the plurality of selectable third-party suppliers in accordancewith the transmitted supplier model.
 11. The software of claim 8,wherein the generated requests are automatically routed to the differentdepartments and the primary supplier using the multi-supplier model. 12.The software of claim 8, further operable to generate a presentationbased, at least in part, on the different aspects of the transaction,wherein transmission of data between the different departments and theprimary supplier are transparent to a user.
 13. The software of claim 8,further operable to: determine data associated with the multi-suppliermodel as processed during operation of the enterprise; and periodicallyupdate the multi-supplier model based, at least in part, on thedetermined data.
 14. The software of claim 8, wherein the softwareoperable to generate the plurality of requests includes the softwareoperable to at least translate data, filter data, or route data betweendifferent network topologies.
 15. A system for managing transactionsexpenses, comprising: memory configured to store a supplier model; andone or more processors configured to: in response to at least a requestfor a enterprise transaction, identify a multi-supplier model configuredto identify information for executing different aspects of thetransaction associated with different enterprise departments and aprimary supplier from a plurality of selectable third-party suppliers,the multi-supplier model configured to identify methodologies forexecuting the different aspects of a transaction; generate a pluralityof requests for the different enterprise departments and the primarysupplier based, at least in part, on the supplier model and thetransaction request, each of the different enterprise departments andthe primary supplier associated with at least one of the plurality ofrequests; identify at least one document for an aspect of thetransaction associated with one of the different enterprise departments;automatically populate said at least one identified document with dataassociated with a corresponding transaction aspect; and automaticallytransmit each of the plurality of requests to at least one of theassociated enterprise departments or the primary supplier in accordancewith the multi-supplier model.
 16. The system of claim 15, theprocessors further configured to: transmit the multi-supplier model toeach of the plurality of selectable third-party suppliers; and receivinginformation associated with different aspects of transactions from theplurality of selectable third-party suppliers in accordance with thetransmitted supplier model.
 17. The system of claim 15, wherein thegenerated requests are automatically routed to the different departmentsand the primary supplier using the multi-supplier model.
 18. The systemof claim 15, the processors further configured to generate apresentation based, at least in part, on the different aspects of thetransaction, wherein transmission of data between the differentdepartments and the primary supplier are transparent to a user.